This page last changed on Aug 28, 2005 by rossmason.

The EjbContainerContext can be used to expose EJB Session beans as Mule components. To configure an Ejb container you need to add a <container-context> element that uses the org.mule.impl.container.EjbContainerContext and set the Jndi environment properties.
The following example configures a JBoss Ejb container context -

<container-context className="org.mule.impl.container.EjbContainerContext">
   <properties>
       <!-- Jndi environment properties -->
       <map name="environment">
          <property name="java.naming.factory.initial" value="org.jnp.interfaces.NamingContextFactory"/>
          <property name="java.naming.provider.url" value="jnp://localhost"/>
          <property name="java.naming.factory.url.pkgs" value="org.jboss.naming:org.jnp.interfaces"/>
       </map>
       
       <!-- optional properties to configure custom security policies and security manager -->
       <property name="securityPolicy" value="/projects/foo/classes/wideopen.policy"/>
       <property name="securityManager" value="java.rmi.RMISecurityManager"/>
   </properties>
</contianer-context>

Components can reference an Ejb session bean by setting the implementation attribute of a <mule-descriptor> to the name of the Session bean stored in Jndi.

<mule-descriptor name="EJBComponent" implementation="myEjbRef">
    ....
</mule-descriptor>
Document generated by Confluence on Nov 27, 2006 10:27